System, method and computer readable medium for billing tolls

ABSTRACT

Billing tolls accumulated during a rental period comprises a third party entity, a toll authority, and a toll rental entity coupled to the third party entity and to the toll authority, wherein the third party entity sends a request for service to the toll rental entity, wherein the toll rental entity sends the request for service during the rental period to the toll authority, wherein the toll authority stores the request, wherein the toll authority sends toll data to the toll rental entity based on the request, wherein the toll rental entity sends toll rental data to the third party entity based on the toll data, and wherein the third party entity generates a bill based on the toll rental data.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present patent application claims priority from U.S. ProvisionalPatent Application No. 60/714,717, titled Toll Fee System And MethodUsing License Plate Recognition, filed on Sep. 07, 2005, the entirecontents of which is incorporated by reference herein.

The present patent application is also related to U.S. Non-ProvisionalPatent Application No. 11/125,521, titled Toll Fee System And Method,filed on May. 10, 2005, and to U.S. Non-Provisional Patent ApplicationDocket No. RTL008, titled System, Method, And Computer Readable MediumFor Billing, filed on even date herewith, the entire contents of each ofwhich are incorporated by reference herein.

FIELD OF THE INVENTION

The present invention is generally related to billing, and morespecifically, to systems, methods, and computer readable media forbilling tolls.

BACKGROUND OF THE INVENTION

The use of a device that permits a vehicle to pass through a toll gatewithout having to physically pay a charge is well known in the art. Suchdevices, referred to as tags, passes, or tracking devices, wirelesslytransmit information to toll gate equipment that results in a charge foruse of a toll road. Problems arise, however, when a rented vehicleutilizes a toll road. In such a scenario, an individual operating therented vehicle must stop at a toll gate and physically pay currencyleading to delays that are not usually experienced by vehicles usingsuch devices.

SUMMARY OF THE INVENTION

A need exists to provide a seamless capability for billing tollsaccumulated during a rental period or a service period in order toovercome the aforementioned problems.

In one embodiment of the present invention, a toll fee tracking systemcomprises a toll authority that collects data associated with a vehicleusing license plate recognition and a toll rental entity thatcommunicates with the toll authority and a third party.

In another embodiment of the present invention, a system for billingtolls accumulated during a rental period comprises a third party entity,a toll authority, and a toll rental entity coupled to the third partyentity and to the toll authority, wherein the third party entity sends arequest for service to the toll rental entity, wherein the toll rentalentity sends the request for service during the rental period to thetoll authority, wherein the toll authority stores the request, whereinthe toll authority sends toll data to the toll rental entity based onthe request, wherein the toll rental entity sends toll rental data tothe third party entity based on the toll data, and wherein the thirdparty entity generates a bill based on the toll rental data.

In a further embodiment of the present invention, a method for billingtolls accumulated during at least one of: a rental period and a serviceperiod comprises sending a service request to a toll authority, whereinthe service request is associated with a license plate number, receivinglicense plate images from the toll authority, providing a charge duringthe rental period if one of the received license plate images equates tothe license plate number associated with the service request, andproviding a violation during the rental period if one of the receivedlicense plate images does not equate to the license plate numberassociated with the service request.

In yet another embodiment of the present invention, a system comprises afirst module that receives a service request, wherein the servicerequest is associated with a license plate number, and a second modulethat sends the service request and a payment associated with the servicerequest, wherein the payment is utilized to provide a service at a tollauthority.

In yet a further embodiment of the present invention, a computerreadable medium comprises instructions for: receiving a service requestcomprising at least a license plate number, receiving a payment relatedto the service request, sending the payment to a toll authority,receiving toll usage information from the toll authority, if the tollusage is related to the license plate number, sending an acknowledgementto the toll authority, and if the toll usage is not related to thelicense plate number, sending a violation to the toll authority.

In yet another embodiment of the present invention, a system for billingtolls accumulated during a service period comprises a third partyentity, a toll authority, and a toll rental entity coupled to the thirdparty entity and to the toll authority, wherein the third party entitysends a request for service to the toll rental entity, wherein the tollrental entity sends the request for service during the service period tothe toll authority, and wherein the toll authority sends toll data and abill to the toll rental entity based on the request.

In yet a further embodiment of the present invention, a computerreadable medium comprises instructions for: sending a payment to a tollauthority, receiving a violation notification from a toll authority,wherein the violation identifies a transport, and obviating theviolation if the payment was intended for the transport.

In yet another embodiment of the present invention, a method for billingtolls comprises capturing at least one picture of a license plate of avehicle, charging the vehicle if a number associated with the capturedlicense plate is listed in a toll rental entity database, and marking atoll violation if the number associated with the captured license plateis not listed in the toll rental entity database.

In yet a further embodiment of the present invention, a toll rentalentity server that communicates toll billing data during a serviceperiod between a toll authority and a third party entity, the tollrental entity server comprises a first interface that communicates withthe toll authority, at least one database, a second interface thatcommunicates with the third party entity, wherein the communicationbetween the toll authority and the third party entity occurs inreal-time, wherein the toll rental entity server: receives a request forservice from the third party entity, sends the request for serviceduring the service period to the toll authority, and receives, based onthe request, toll data and a bill from the toll authority.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a block diagram of a license plate recognition module inaccordance with an embodiment of the present invention;

FIG. 2 depicts a license plate recognition module installed on anelectronic toll collection lane;

FIG. 3 depicts a block diagram of a system in accordance with anembodiment of the present invention;

FIG. 4 depicts a block diagram of a system in accordance with analternate embodiment of the present invention;

FIG. 5 depicts a flow diagram illustrating a method in accordance withan embodiment of the present invention;

FIG. 6 a depicts a flow chart for billing tolls in accordance with anembodiment of the present invention;

FIG. 6 b depicts an alternate flow chart for billing tolls in accordancewith an embodiment of the present invention;

FIG. 6 c depicts a message flow for billing tolls in accordance with anembodiment of the present invention;

FIG. 6 d depicts a relational system in accordance with an embodiment ofthe present invention;

FIG. 7 depicts a flow diagram illustrating a method for billing tolls inaccordance with an embodiment of the present invention;

FIG. 8 depicts a system with emphasis on the toll rental entity inaccordance with an embodiment of the present invention;

FIG. 9 depicts a flow diagram illustrating a computer readable medium inaccordance with an embodiment of the present invention;

FIG. 10 depicts a flow diagram illustrating a service request andpayment being sent in accordance with an embodiment of the presentinvention; and

FIG. 11 depicts a flow diagram illustrating a computer readable mediumin accordance with an alternate embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Referring now to FIG. 1, a block diagram of a license plate recognitionmodule or system 100 is illustrated. License Plate Recognition (LPR) isan image processing technology used to identify vehicles by theirlicense plates. This system 100 uses camera and illumination (infra-red)to capture the vehicle images, with the help of image processingsoftware. License plate number information will be extracted from theimage. The module not only captures the vehicle image but also extractsthe license plate number as a string for toll rental entity transactionsand toll violation processing.

The LPR module 100 includes a sensor (not shown) which detects a vehiclecoming into a toll authority. The presence of the vehicle is signaled tothe illumination and camera unit for image capturing. The LPR module 100further includes a camera and illumination unit 102. The camera andillumination unit 102 captures the front and rear side of the vehicleand brightens up a license plate of the vehicle such that clear imagesof the license plate of vehicles can be taken at any time. Theillumination in most cases is Infra-Red (IR) which is invisible to thedriver. In addition, the LPR module 100 includes a PC adapter 104 whichis a hardware interface connecting the camera 102 and PC 106 to capturethe image in the LPR module 100. The LPR software captures, analyzes andidentifies the license plate number of vehicles and interface it withtoll rental entity for authentication.

Low recognition rate is one of the key issues in using LPR software.This is due to the external efforts such as sun and headlights, badlicense plates, and also due to the hardware and software quality used.Thorough testing and benchmarking are required to evaluate LPR systems.Transit speed up to 75 mph should be easily manageable by the system.Recognition rates of generic license plates (data collection) should be99.99%. Those are the critical requirements to select LPR modules 100for a toll rental entity interface.

Referring now to FIG. 2, a license plate recognition module 100installed on an electronic toll collection lane is illustrated.

Referring now to FIG. 3, a block diagram of a system of the presentinvention includes a toll rental entity 300 that interfaces with both atoll authority 302 and a third party entity 304. The toll rental entity300 interacts with the toll authority 302 via a toll authority interface306 and the third party entity 304 via a third party entity interface308. The toll authority 302 maintains various toll gates 310, LPRmodules 312 for communicating with the toll gates, and collects tolldata that is stored in a toll database 314. The third party entity 304sends a request (for example, a request for service) and includes a tollrental interface 318 that receives toll data from the toll rental entitybased on the request, and a fee reconciliation unit 320 that providesaccount and/or billing functionality based on the received toll rentaldata. In alternate embodiments, any of these aforementioned module orelements may provide the functionality described or depicted.

Referring now to FIG. 4, an alternate embodiment of a system of thepresent invention is illustrated. The toll rental system may beintegrated into an existing operating system of the third party entityor rental agency 304. The rental agency 304 may request data directlyfrom the toll authority 302. The rental agency 304 can then store tollrental data and reconcile accounts.

Referring now to FIG. 5, a flow diagram of a method 500 of an embodimentof the present invention is shown. To access tolls incurred by vehicles,the toll rental entity, or other entity, equips the toll authoritieswith LPR modules. At step 502, a vehicle approaches the toll authorityafter which the sensor is initiated (step 504). At step 506, thepresence of a vehicle is signaled to the LPR module. At step 508, LPRsoftware activates the illumination (invisible IR in most cases) andtakes pictures of the front and/or rear license plates of vehicles fromthe LPR camera. The images of the vehicle include the plate and thepixel information provided by the LPR unit's image processing hardware(PC adapter). At step 510, the LPR software analyzes the image withdifferent image processing software algorithms, enhances the image,detects the vehicle license plate position, extracts the license platestring, and identifies the fonts using special artificial intelligencemethods (such as Neural Networks). At step 512, the toll rental entitycaptures the pictures. At step 514, the toll rental entity performs anauthentication procedure in the toll rental entity server. If thevehicle license plate number is listed in the toll rental entitydatabase, the vehicle will be charged for the toll usage (step 518). Theprocess ends at step 520. If the vehicle license plate number is notlisted in the toll rental entity database will be marked as tollviolation (step 516) and the process proceeds to step 502.

Referring now to FIG. 6 a, a flow chart 600 for billing tolls for fleetscomprises a third party entity that sends fleet information such aslicense plate numbers and states of each transport owned and/orassociated with the fleet to a toll rental entity in step 602. The tollrental entity saves the fleet information in a toll rental entitydatabase in step 604, and sends the fleet information to a tollauthority in step 606. In steps 608 and 610, respectively, the tollauthority saves the fleet information in a toll authority database, andsends toll data related to the fleet information to the toll rentalentity. The toll rental entity sends the toll data and an invoice forthe toll data to the third party entity at step 612, the third partyentity sends a payment to the toll rental entity at step 614, and thetoll rental entity sends the payment to the toll authority at step 616.

In alternate embodiments of the present invention, the toll rentalentity may directly send the fleet information to the toll authoritywithout or before saving the fleet information. Further, the tollauthority may send the toll data related to the fleet information to thetoll rental entity without or before saving the fleet information in thetoll authority database. Also, all, or a portion of, the data orinformation mentioned herein can be stored in one or more of thedescribed databases.

In further alternate embodiments of the present invention, a third partyentity sends fleet license plate numbers, state information, and thelike as toll data to the toll rental entity which saves this data in adatabase and/or transfers it to the toll authority which stores it in adatabase. As the fleet uses the toll authority's toll gates or lanes,the toll authority compares the fleet usage information with informationstored in their database and sends this usage information, a time anddate of the usage and the like to the toll rental entity.

In other embodiments of the present invention, charges associated withsuch usage may be sent by the toll authority to the toll rental entity.This data is stored in a database, which may be the same database thefleet information is stored in, and is sent to the third party entity.The third party entity sends a service request to the toll rental entityand is stored in a database which may be the same as the aforementioneddatabase. A check is performed to determine if the service request isfound. If it is, a notification and a payment are sent to the tollauthority along with service details. Such a payment may be madeimmediately or after some time has elapsed. If the service request isnot found, a violation is noted and stored in a different or in a samedatabase as previously mentioned, and is sent to the third party entity.In this scenario, a fleet is proactively registered by the toll rentalentity as a service request for a rental agreement may not be sent tothe toll authority.

Referring now to FIG. 6 b, a flow chart 620 for billing tolls comprisesa third party entity that sends a service request to a toll rentalentity at step 622. At steps 624 and 626, respectively, the toll rentalentity stores the service request in a toll rental entity database, andsends a service request and a deposit for the service request to a tollauthority. At step 628 the toll authority sends toll data to the tollrental entity for matched and unmatched service requests, and at step630 the toll rental entity receives the toll data from the tollauthority. At step 632, a check is made in order to determine if theservice request is found for the toll data. If it is, the toll rentalentity sends a payment to the toll authority for any shortage from adeposit account for the toll data at step 634. If the service request isnot found for the toll data, the toll rental entity sends a tollviolation and an invoice for the toll violation to the third partyentity at step 636. The third party entity sends a payment to the tollrental entity for toll data and violation fees, and the toll rentalentity sends the payment to the toll authority for the toll data insteps 638 and 640, respectively.

In alternate embodiments of the present invention, a system for billingtolls accumulated during a rental period comprises a third party entity,a toll authority, and a toll rental entity coupled to the third partyentity and to the toll authority, wherein the third party entity sends arequest for service to the toll rental entity, wherein the toll rentalentity sends the request for service during the rental period to thetoll authority, wherein the toll authority stores the request, whereinthe toll authority sends toll data to the toll rental entity based onthe request, wherein the toll rental entity sends toll rental data tothe third party entity based on the toll data, and wherein the thirdparty entity generates a bill based on the toll rental data. In thisscenario, a service request for a rental agreement is sent to the tollauthority.

In the system, the third party entity receives information related to anindividual or an entity wishing to rent a transport, wherein theinformation includes information of the individual or the entity andinformation regarding the transport, and wherein the individual'sinformation includes at least one of: the individual's name, theindividual's address, the individual's driver license number, theindividual's driver license state, the individual's credit card number,the individual's debit card number, the individual's electronic accountnumber, the individual's insurance information, the individual's emailaddress, and the individual's phone number.

The entities' information includes at least one of: a name of theentity, an address of the entity, a phone number of the entity, an emailaddress of the entity, a contact person for the entity, an email addressof the contact person, a tax identification number, a credit card numberfor the entity, and a bank number for the entity, wherein theinformation regarding the transport includes at least one of: an ownerof the transport, a license plate number of the transport, a vehicleidentification number of the transport, an identification of the number(via, for example, the use of radio frequencies, nanotechnology, and thelike), a type of the transport, a color of the transport, a year ofmanufacture of the transport, and a condition of the transport, whereinthe request for service includes at least one of: an individual's namerequesting the service, a license plate number of a transport that is tobe utilized, a payment for the service, and rental contract informationrelated to the transport, wherein the rental contract includes at leastone of: a start date and a start time, and an end date and an end time,wherein service begins at a date and a time that the transport leaves aparticular area, and wherein service ends at a date and a time that thetransport returns to the particular area, and wherein service begins ata date and a time that the transport leaves a particular area, andwherein service ends at a date and a time that the transport returns toa different area.

The toll data includes at least one of: information related totransport, information related to a license plate of the transport, alocation of the transport, a direction of the transport, a time stamprelated to the transport, and a toll amount incurred by the transport,wherein the toll rental data includes information related to thetransport based on at least one of: a reading of a license plate of thetransport, to an individual associated with the request, and to anentity associated with the request, and wherein the third party entityis at least one of: a rent-a-car entity, an entity that rents transportscomprising license plates, an entity that rents transports comprisinginformation that can be acquired, an entity or individual that ownstransports, an entity or individual that leases transports, an entity orindividual that loans transports, an entity or individual that lendstransports, and an entity or individual that operates transports.

The third party entity generates a bill in at least one of: before therental period, during the rental period, at an end of the rental period,and at a time after the end of the rental period, wherein the request,the toll data, and the toll rental data is sent in at least one of afollowing medium: wireless, and wired, and wherein the bill is generatedto at least one of: a transport operator, a transport or entity renter,a transport or entity owner, a transport or entity leaser, a transportor entity loaner and, a transport or entity lender.

Referring now to FIG. 6 c, a message flow 650 depicts originatingsources and terminating destinations for a number of messages. A servicerequest and payment message may be sent in the following scenarios: byan individual 652 to a business 654, by the individual to a third partyentity 656, by the third party entity to a toll rental entity 658, bythe toll rental entity to a toll authority 660, by the business to thetoll rental entity, and by the individual to the toll rental entity. Inresponse to the service request and payment message, a toll data andpayment message or a toll data message may be sent in the followingscenarios: by a toll rental entity 658 to a business 654, by the tollrental entity to an individual 652, by a third party entity 656 to thebusiness, by a toll authority 660 to the toll rental entity, by the tollrental entity to the third party entity, by the third party entity tothe individual, and by the business to the individual.

In alternate embodiments of the present invention, the service requestand the payment, the toll data and the payment, and/or the toll data maybe sent and/or received by any of the sources and destinations. Further,the service request and the payment and/or the toll data and the paymentmay be sent independently or not at all.

Referring now to FIG. 6 d, a relational system in accordance with anembodiment of the present invention is depicted. The system includes anindividual 672, a business, toll authority, or other entity (such as atoll tag or device manufacturer, a mobile device manufacturer, etc,)674, a third party entity 676, and a toll rental entity 678. Each ofthese entities or individual can communicate with one another and mayperform a variety of actions such as requesting service, performingbilling functions, accumulating and providing metrics, and the like.

Referring now to FIG. 7, a method 700 for billing tolls comprisesreceiving a service request from a third party entity at step 702,receiving a payment from the third party entity at step 704, sending aservice request to a toll authority (with a payment or without apayment) at step 706, receiving toll data from the toll authority atstep 708, sending an acknowledgement to the toll authority at step 710,and sending the toll data to the third party entity (or to theindividual and/or to another entity) at step 712.

In an alternate embodiment of the present invention, a method forbilling tolls accumulated during at least one of: a rental period and aservice period comprises sending a service request to a toll authority,wherein the service request is associated with a license plate number,receiving license plate images from the toll authority, providing acharge during the rental period if one of the received license plateimages equates to the license plate number associated with the servicerequest, and providing a violation during the rental period if one ofthe received license plate images does not equate to the license platenumber associated with the service request. The transport's serviceperiod may last for a longer time frame than the rental period which mayoccur if the transport's service area (for example, city or state)differs from the rental area. For example, the service period may lastfor three weeks in the Dallas area. However, a rental period within theservice period may occur when the transport is driven to Houston for afew days. In such a scenario, the service request, usage, and tollcharges may differ than those with the service period. In anotherembodiment, a method for billing tolls accumulated during at least oneof: a rental period and a service period, the method comprises sending aservice request associated with a license plate number to a tollauthority, wherein the service request is associated with a licenseplate number, receiving a plurality of license plate images from thetoll authority, comparing license plate numbers corresponding to thereceived plurality of license plate images with the license plate numberassociated with the service request, providing a charge during therental period if one of the charging an account responsive to a licenseplate number corresponding to a license plate image of the receivedplurality of license plate received license plate images matching thelicense plate number associated with the service request equates to thelicense plate number associated with a the service request, and charginga violation fee responsive to a license plate number corresponding to alicense plate image of the received plurality of license plate imagesnot matching the license plate number associated with the servicerequest.

The method comprises receiving time stamps and locations from the tollauthority, collecting the license plate images, the time stamps, and thelocations when transports utilize the toll authority, and sending apayment associated with the license plate number when the servicerequest to the toll authority is sent, wherein the payment is sent inlieu of providing the charge during at least one of the periods, whereinthe payment is sent in lieu of providing the violation during at leastone of the periods. For example, the payment may be sent before a propercharge or a violation has occurred.

The method comprises providing a charge during at least one of theperiods if one of the received license plate images is similar to thelicense plate number associated with the service request and providing aviolation during at least one of the periods if one of the receivedlicense plate images is not similar to the license plate numberassociated with the service request. We may get input from a thirdparty.

Referring now to FIG. 8, a system 800 comprises a first module 802 thatreceives a service request, wherein the service request is associatedwith a license plate number, and a second module 804 that sends theservice request and a payment associated with the service request,wherein the payment is utilized to provide a service at a toll authority806. The payment can be sent prior to the service, during the service,after the service, for a certain period, for a rental period, for aservice period, and by at least one of: at least one toll rental entity,and at least one third party entity.

The first module 802 receives the service request from at least one of:at least one third party entity 808, and at least one toll authority806, wherein the first module sends information to the third partyentity, wherein the second module 804 sends the service request to thetoll authority, and wherein the second module receives information fromthe toll authority. The system may also comprise a third module (such asan individual, a business, or other entity) that receives informationfrom at least one of: the first module, and the second module. Althoughdepicted as separate modules, the first module 802 and the second module804 may be combined into one module or may be kept separate and be apart of another module (not shown).

Referring now to FIG. 9, a flow chart 900 of a computer readable mediumof the present invention is depicted. The computer readable mediumcomprises instructions for: receiving a service request comprising atleast a license plate number 902, receiving a payment related to theservice request 904, sending a payment to a toll authority 906,receiving toll data such as toll usage information from the tollauthority 908, and determining if the if the toll usage is related tothe license plate number 910. If the toll usage is related to thelicense plate number, sending an acknowledgement to the toll authority912, and if the toll usage is not related to the license plate number,sending a violation to the toll authority 914. In another embodiment ofthe present invention, if the toll usage is not related to the licenseplate number, sending a notification of a license plate number that isnot found to the toll authority.

The computer readable medium comprises instructions for receiving theservice request before a transport is rented, wherein the paymentcoincides with a first rate, and comprises instructions for receivingthe service request after a transport is rented, wherein the paymentcoincides with a second rate. For example, an individual may not haverequested service upon renting the transport but later decides torequest service and thus may be faced with a higher payment and/or withdifferent terms.

Referring now to FIG. 10, a system 1000 for billing tolls accumulatedduring a service period comprises a third party entity 1002, a tollrental entity 1004 and a toll authority 1006, wherein the toll rentalentity is coupled to the third party entity and to the toll authority,wherein the third party entity sends a request for service to the tollrental entity, wherein the toll rental entity sends the request forservice during the service period to the toll authority, and wherein thetoll authority sends toll data and a bill to the toll rental entitybased on the request. For example, a third party entity may be a rentalcar company, boat rental company, fleet trucking company, plane rentalcompany, train rental company, bus rental company, new car fleet dealer,used car fleet dealer, transport manufacturer, etc. In other embodimentsof the present invention, a system for billing tolls accumulated duringa service period, comprises a third party entity, a toll authority, atoll rental entity adapted to receive a request for service from thethird party entity, send the request for service during the serviceperiod to the toll authority, and receive, based on the request, tolldata and a bill from the toll authority.

Referring now to FIG. 11, a flow chart 1100 of a computer readablemedium of the present invention is depicted. The computer readablemedium comprises instructions for: sending a payment to a toll authority1102, and receiving a violation notification or toll transactionnotification from the toll authority 1104, wherein the violationidentifies a transport, and obviating the violation or processing thetoll transaction if the payment was intended for the transport 1106.

Although an exemplary embodiment of the system of the present inventionhas been illustrated in the accompanied drawings and described in theforegoing detailed description, it will be understood that the inventionis not limited to the embodiments disclosed, but is capable of numerousrearrangements, modifications, and substitutions without departing fromthe spirit of the invention as set forth and defined by the followingclaims. For example, the capabilities of the invention can be performedfully and/or partially by one or more of the described or depictedelements. Also, these capabilities may be performed in the currentmanner or in a distributed manner and on, or via, any device able toprovide and/or receive information. Further, although depicted in aparticular manner, various modules or blocks may be repositioned withoutdeparting from the scope of the current invention. For example,information being sent to the toll rental entity can be sent to thethird party entity or to multiple third party entities or may be sent toone of the entities in lieu of the other. Still further, althoughdepicted in a particular manner, a greater or lesser number of elementsand connections can be utilized with the present invention in order toaccomplish the present invention, to provide additional known featuresto the present invention, and/or to make the present invention moreefficient. For example, a toll tag or other electronic device can beused to send, receive, and/or store any of the data described ordepicted herein. Also, the information sent between various elementsdescribed or depicted herein, can be sent via a wireless source and/or awired source and via a plurality of protocols.

1. A system for billing tolls accumulated during a rental period,comprising: a third party entity; a toll authority; and a toll rentalentity coupled to the third party entity and to the toll authority;wherein the third party entity sends a request for service to the tollrental entity; wherein the toll rental entity sends the request forservice during the rental period to the toll authority; wherein the tollauthority stores the request; wherein the toll authority sends toll datato the toll rental entity based on the request; wherein the toll rentalentity sends toll rental data to the third party entity based on thetoll data; and wherein the third party entity generates a bill based onthe toll rental data.
 2. The system of claim 1, wherein the third partyentity receives information related to an individual or an entitywishing to rent a transport.
 3. The system of claim 2, wherein theinformation includes information of the individual or the entity andinformation regarding the transport.
 4. The system of claim 3, whereinthe individual's information includes at least one of: the individual'sname; the individual's address; the individual's driver license number;the individual's driver license state; the individual's credit cardnumber; the individual's debit card number; the individual's electronicaccount number; the individual's insurance information; the individual'semail address; and the individual's phone number.
 5. The system of claim3, wherein the entities' information includes at least one of: a name ofthe entity; an address of the entity; a phone number of the entity; anemail address of the entity; a contact person for the entity; an emailaddress of the contact person; a tax identification number; a creditcard number for the entity; and a bank number for the entity.
 6. Thesystem of claim 3, wherein the information regarding the transportincludes at least one of: an owner of the transport; a license platenumber of the transport; a vehicle identification number of thetransport; an identification of the number; a type of the transport; acolor of the transport; a year of manufacture of the transport; and acondition of the transport.
 7. The system of claim 1, wherein therequest for service includes at least one of: an individual's namerequesting the service; a license plate number of a transport that is tobe utilized; a payment for the service; and rental contract informationrelated to the transport, wherein the rental contract includes at leastone of: a start date and a start time; and an end date and an end time.8. The system of claim 1, wherein the service begins at a date and atime that a transport leaves a particular area, and wherein the serviceends at a date and a time that the transport returns to the particulararea.
 9. The system of claim 1, wherein the service begins at a date anda time that a transport leaves a particular area, and wherein theservice ends at a date and a time that the transport returns to adifferent area.
 10. The system of claim 1, wherein the toll dataincludes at least one of: information related to a transport;information related to a license plate of the transport; a location ofthe transport; a direction of the transport; a time stamp related to thetransport; and a toll amount incurred by the transport.
 11. The systemof claim 1, wherein the toll rental data includes information related toa transport based on at least one of: a reading of a license plate ofthe transport, to an individual associated with the request, and to anentity associated with the request.
 12. The system of claim 1, whereinthe third party entity is at least one of: a rent-a-car entity; anentity that rents transports comprising license plates; an entity thatrents transports comprising information that can be acquired; an entityor individual that owns transports; an entity or individual that leasestransports; an entity or individual that loans transports; an entity orindividual that lends transports; and an entity or individual thatoperates transports.
 13. The system of claim 1, wherein the third partyentity generates a bill in at least one of: before the rental period;during the rental period; at an end of the rental period; and at a timeafter the end of the rental period.
 14. The system of claim 1, whereinthe request, the toll data, and the toll rental data is sent in at leastone of a following medium: wireless; and wired.
 15. The system of claim1, wherein the bill is generated to at least one of: a transportoperator; a transport or entity renter; a transport or entity owner; atransport or entity leaser; a transport or entity loaner and; atransport or entity lender.
 16. A method for billing tolls accumulatedduring at least one of: a rental period and a service period,comprising: sending a service request to a toll authority, wherein theservice request is associated with a license plate number; receivinglicense plate images from the toll authority; providing a charge duringthe rental period if one of the received license plate images equates tothe license plate number associated with the service request; andproviding a violation during the rental period if one of the receivedlicense plate images does not equate to the license plate numberassociated with the service request.
 17. The method of 16 comprisingreceiving time stamps and location information from the toll authority.18. The method of claim 17 comprising collecting the license plateimages, the time stamps, and the location information when transportsutilize the toll authority.
 19. The method of claim 16 comprisingsending a payment associated with the license plate number when theservice request to the toll authority is sent.
 20. The method of claim19, wherein the payment is sent in lieu of providing the charge duringat least one of the periods.
 21. The method of claim 19, wherein thepayment is sent in lieu of providing the violation during at least oneof the periods.
 22. The method of claim 16 comprising providing a chargeduring at least one of the periods if one of the received license plateimages is similar to the license plate number associated with theservice request.
 23. The method of claim 16 comprising providing aviolation during at least one of the periods if one of the receivedlicense plate images is not similar to the license plate numberassociated with the service request.
 24. A system, comprising: a firstmodule that receives a service request, wherein the service request isassociated with a license plate number; and a second module that sendsthe service request and a payment associated with the service request,wherein the payment is utilized to provide a service at a tollauthority.
 25. The system of claim 24, wherein the payment is sent priorto the service.
 26. The system of claim 24, wherein the payment is sentduring the service.
 27. The system of claim 24, wherein the payment issent after the service.
 28. The system of claim 24, wherein the paymentis sent for a certain period.
 29. The system of claim 24, wherein thepayment is sent for a rental period.
 30. The system of claim 24, whereinthe payment is sent for a service period.
 31. The system of claim 24,wherein the payment is sent by at least one of: at least one toll rentalentity; and at least one third party entity.
 32. The system of claim 24,wherein the first module receives the service request from at least oneof: at least one third party entity; and at least one toll authority.33. The system of claim 24, wherein the first module sends informationto a third party entity.
 34. The system of claim 24, wherein the secondmodule sends the service request to a toll authority.
 35. The system ofclaim 24, wherein the second module receives information from a tollauthority.
 36. The system of claim 24 comprising a third module thatreceives information from at least one of: the first module; and thesecond module.
 37. A computer readable medium comprising instructionsfor: receiving a service request comprising at least a license platenumber; receiving a payment related to the service request; sending thepayment to a toll authority; receiving toll usage information from thetoll authority; if the toll usage is related to the license platenumber, sending an acknowledgement to the toll authority; and if thetoll usage is not related to the license plate number, sending aviolation to the toll authority.
 38. The computer readable medium ofclaim 37 comprising instructions for receiving the service requestbefore a transport is rented.
 39. The computer readable medium of claim38, wherein the payment coincides with a first rate.
 40. The computerreadable medium of claim 37 comprising instructions for receiving theservice request after a transport is rented.
 41. The computer readablemedium of claim 40, wherein the payment coincides with a second rate.42. A system for billing tolls accumulated during a service period,comprising: a third party entity; a toll authority; and a toll rentalentity coupled to the third party entity and to the toll authority;wherein the third party entity sends a request for service to the tollrental entity; wherein the toll rental entity sends the request forservice during the service period to the toll authority; and wherein thetoll authority sends toll data and a bill to the toll rental entitybased on the request.
 43. A computer readable medium comprisinginstructions for: sending a payment to a toll authority; receiving aviolation notification from a toll authority, wherein the violationidentifies a transport; and obviating the violation if the payment wasintended for the transport.
 44. A method for billing tolls, comprising:capturing at least one picture of a license plate of a vehicle; chargingthe vehicle if a number associated with the captured license plate islisted in a toll rental entity database; and marking a toll violation ifthe number associated with the captured license plate is not listed inthe toll rental entity database.
 45. A toll rental entity server thatcommunicates toll billing data during a service period between a tollauthority and a third party entity, the toll rental entity servercomprising: a first interface that communicates with the toll authority;at least one database; a second interface that communicates with thethird party entity; wherein the communication between the toll authorityand the third party entity occurs in real-time; wherein the toll rentalentity server: receives a request for service from the third partyentity; sends the request for service during the service period to thetoll authority; and receives, based on the request, toll data and a billfrom the toll authority.